<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<title>Business Case</title>

</head>

<body>
<table border="0" cellspacing="0" cellpadding="0" align="left" width="100%">
  <tr>
    <td width="468" valign="top"><p><a href="./inception.html">Home</a></td>
    <td width="491" valign="top"><p align="right"><a href="1.20_objective.html">Next</a></td>
  </tr>
</table>
<p><em>Business Case</em></p>
<p>&lt;&lt; The Business Case defines  how the customer  will derive value from the solution. It connects the customer’s business goals  to the specific performance expectations realized from the solution. This  information should include an estimate of solution cost and how that investment  will be converted into savings and/or revenue for the customer.  Performance expectations should  be expressed numerically with all investments  to showing a return. Developing this section assists the team in understanding  the project’s overarching drivers<strong>.  &gt;&gt;</strong></p>

<p><strong>Opportunity</strong><strong> </strong><br>
&lt;&lt; The Business Opportunity section contains the statement of the  customer’s situation. It is expressed in business language, not technical  terms. This section should demonstrate the organizations understanding of the  customer’s current environment and its desired future state. This information  is the overall context for the project. Benefits Analysis demonstrates that  organization sufficiently understands the customer’s situation and business  needs.  &gt;&gt;</p>
<p><strong>Opportunity</strong><strong> Statement</strong><strong> </strong><br>
&lt;&lt; The Opportunity  Statement section describes the customer’s current situation that creates the  need for the project. It may contain a statement of the customer’s opportunity  and the impact of capitalizing on that opportunity (product innovation, revenue  enhancement, cost avoidance, operational streamlining, and leveraging  knowledge). It may contain a statement of the customer’s problem and the impact  of solving the problem (revenue protection, cost reduction, regulatory  compliance, alignment of strategy and technology). It should include a  statement that connects the customer’s opportunity/problem to the relevant  business strategy and drivers. The Opportunity Statement is written concisely  using a business executive’s voice.  The  Opportunity Statement demonstrates that organization understands the customer’s  situation from the business point of view.   &gt;&gt;</p>
<p>&lt;&lt; What problem is solving by engaging in activity? &gt;&gt;</p>
<p>&lt;&lt; Will activity increase profits or decrease costs?  Explain How? &gt;&gt; </p>
<p>&lt;&lt; What are the success criteria of activity? &gt;&gt;</p>
<p>&lt;&lt; How much would customers paid to use the product or service?  &gt;&gt; </p>
<p>&lt;&lt; What will happen to the business if activity is not  undertaken? &gt;&gt;</p>
<p>&lt;&lt; What will  happen to the business if activity is not undertaken? &gt;&gt;</p>
<p>&lt;&lt; How much  would customers paid to use the product or service? &gt;&gt;</p>

<p><strong>Brand  Loyalty - </strong><strong>&lt;&lt; </strong>How will activity increase customer loyalty? &gt;&gt;</p>
<p><strong>Efficiency  -</strong> <strong>&lt;&lt; </strong>How will activity decrease costs by increasing  operational efficiency. &gt;&gt;<br>
  <br>
  <strong>Revenue  - &lt;&lt; </strong>How will activity increase? Explain how?   &gt;&gt;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
</body>
</html>
